Posts

Post marked as solved
2 Replies
To follow up: I figured out what was wrong and it was a doozie. I have a pretty large app that is built using multiple projects under one workspace. Each project builds and then they are all linked together. My MetalViewController class was under my Engine project. My story board is in my AppMain project. Turns out that when the linking takes place, because my MetalViewController wasn't linked to other code the linker would strip it out. (Apparently the linker doesn't care about what the story board might link to in other projects) When the app would run, there would be no warning, or anything.To fix this, I created a subclass of my MetalViewController and included that subclass in my AppMain project. Then set my story board to have the view controller point to my subclass. And in my subclass' call to viewDidLoad I simply call [super viewDidLoad] ; which of course calls my MetalViewController's viewDidLoad.Once that was set up my MetalViewController's functions started being being called and the graphics started drawing into the view controller. (Yeah!)But I have to say, this is the sort of thing that Apple should be providing warnings about. The fact that I figured this out is largely dumb luck.